Unified GUI adaptation in Dynamic Software Product Lines

In the modern world of mobile computing and ubiquitous technology, society is able to interact with technology in new and fascinating ways. To help provide an improved user experience, mobile software should be able to adapt itself to suit the user. By monitoring context information based on the environment and user, the application can better meet the dynamic requirements of the user. Similarly, it is noticeable that programs can require different static changes to suit static requirements. This program commonality and variability can benefit from the use of Software Product Line Engineering, reusing artefacts over a set of similar programs, called a Software Product Line (SPL). Historically, SPLs are limited to handling static compile time adaptations. Dynamic Software Product Lines (DSPL) however, allow for the program configuration to change at runtime, allow for compile time and runtime adaptation to be developed in a single unified approach. While currently DSPLs provide methods for dealing with program logic adaptations, variability in the Graphical User Interface (GUI) has largely been neglected. Due to this, depending on the intended time to apply GUI adaptation, different approaches are required. The main goal of this work is to extend a unified representation of variability to the GUI, whereby GUI adaptation can be applied at compile time and at runtime. In this thesis, an approach to handling GUI adaptation within DSPLs, providing a unified representation of GUI variability is presented. The approach is based on Feature-Oriented Programming (FOP), enabling developers to implement GUI adaptation along with program logic in feature modules. This approach is applied to Document-Oriented GUIs, also known as GUI description languages. In addition to GUI unification, we present an approach to unifying context and feature modelling, and handling context dynamically at runtime, as features of the DSPL. This unification can allow for more dynamic and self-aware context acquisition. To validate our approach, we implemented tool support and middleware prototypes. These different artefacts are then tested using a combination of scenarios and scalability tests. This combination first helps demonstrate the versatility and its relevance of the different approach aspects. It further brings insight into how the approach scales with DSPL size

Weisser, Mary ( Walz) (Blonigan) (1854 - )

This biographical summary was created by the Works Progress Administration (WPA) between 1936 and 1939

Coproporphyria

Click on the link to view

Developing navigational services for people with Down's Syndrome

The ability to commute and travel alone is an important skill that enables people to be more independent, and integrated with society. People with Down's Syndrome often experience low social integration, and low degree of independence. As part of the European Commission funded POSEIDON project, we want to explore how context-aware, and assistive technology can enable users with Down's Syndrome be more independent, including the ability to commute alone to a place of interest. In this paper, we report on our current progress in developing navigational services within the context of the POSEIDON project. We carried out a semi-structured qualitative evaluation of an early version of our navigational services with 6 individuals with Down's Syndrome, and report on our findings

The user-centred intelligent environments development process as a guide to co-create smart technology for people with special needs

We report on the lessons learnt during the application of a methodology to develop Intelligent Environments. One important feature of the methodology is that of being strongly user-centred and we report on how that interaction with users took place and how it continuously shaped our project aspirations and outcomes. The methodology was applied to a project which aimed at helping people with Downs Syndrome and those with similar conditions and needs, to be more included in society. The project was developed by amconsortium of commercial, academic, and end-user supporting organizations. We explain what type of stakeholders engaging activities were considered, how these were distributed along the lifetime of the project and their impact